Revert cri-o freeze #1343
Revert cri-o freeze #1343
Conversation
kubevirt-bot
added
the
dco-signoff: yes
|
/hold /cc @enp0s3 @brianmcarey |
kubevirt-bot
added
the
do-not-merge/hold
|
/retest |
|
so the fix should be in crun, so any cri-o version should work given the correct crun version (1.19) |
@brianmcarey I believe we're consuming crun through the cri-o install? and that does not have 1.19 yet |
|
ah gotcha. 1.31.1 does not have an updated crun. I am trying to figure out a bug I've introduced and once I do that i'll cut a 1.31.2 which will have new crun |
|
@haircommander Hi, if for example we want to consume latest CRIO with latest crun, is there DNF repo that contains nightly RPMs of latest CRIO and crun builds? |
|
@ormergi Hi, do you know if there was a progress since CRIO was pinned? AFAIK it were the network tests that failed to create the network tap device. |
|
@ormergi Sorry I've missed that @akalenyu pointed out https://issues.redhat.com/browse/OCPBUGS-45394 |
|
/retest |
kubevirt-bot
added
the
needs-rebase
…ubevirt#1320)" This reverts commit 6c4fa8f. Signed-off-by: Alex Kalenyuk <[email protected]>
Signed-off-by: Alex Kalenyuk <[email protected]>
akalenyu
force-pushed
the
revert-crio-freeze
branch
from
6cf1c65 to
94883af
Compare
kubevirt-bot
added
size/XS
and removed
needs-rebase
I believe you meant 1.31.4? I am looking at latest (only in crun 1.19 according to release notes) |
|
/retest |
|
/hold cancel we should be okay [root@node01 vagrant]# dnf install -y cri-o
...
Upgraded:
cri-o-1.31.4-150500.1.1.x86_64
Complete!
[root@node01 vagrant]# /usr/libexec/crio/crun --version
crun version 1.19.1 |
kubevirt-bot
removed
the
do-not-merge/hold
|
/retest |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: enp0s3 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
kubevirt-bot
added
the
approved
|
@akalenyu: The following test failed, say
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
[a6a9235 Revert cri-o freeze](kubevirt/kubevirtci#1343) ```release-note NONE ``` Signed-off-by: kubevirt-bot <[email protected]>
The cri-o versions were previously pinned[1] but we should now be good to update to cri-o v1.32 [1] kubevirt#1343 Signed-off-by: Brian Carey <[email protected]>
[a6a9235 Revert cri-o freeze](kubevirt/kubevirtci#1343) ```release-note NONE ``` Signed-off-by: kubevirt-bot <[email protected]>
The cri-o versions were previously pinned[1] but we should now be good to update to cri-o v1.32 [1] #1343 Signed-off-by: Brian Carey <[email protected]>
What this PR does / why we need it:
Once the cri-o issues are fixed, we should continue consuming latest cri-o.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.
Release note: